Conversation
cba1c06 to
08d86fb
Compare
codeboten
left a comment
There was a problem hiding this comment.
This is looking pretty good! Just a couple of questions I'd like to have answered before I approve
|
|
||
| for propagator in self._propagators: | ||
| for field in propagator.fields: | ||
| composite_fields.add(field) |
There was a problem hiding this comment.
is the behaviour for the composite propagator specified in the spec?
There was a problem hiding this comment.
I don't think it is, I tried to replicate the Go implementation with one particular difference. In this implementation a set is returned instead of a list. There is no defined order for these fields (these fields may be called in inject in an arbitrary order and even if this order is constant it has no relation with the fields themselves), so an ordered sequence like a list makes no sense. Also, (if I understand correctly) the intention of this attribute is to allow the user to tell if a certain field is also used in inject. That is an in operation that has a better (O(1)) performance in a set than in a list (O(N)).
19ee9fa to
7d432b9
Compare
579af1a to
92ccbf1
Compare
codeboten
left a comment
There was a problem hiding this comment.
Thanks for addressing my comments.
1ff26a1 to
c76a8f9
Compare
opentelemetry-api/CHANGELOG.md
Outdated
|
|
||
| ## Unreleased | ||
|
|
||
| - Add `fields` to propagators ([#1374](https://github.com/open-telemetry/opentelemetry-python/pull/1374)) |
There was a problem hiding this comment.
The PR link should probably go on a new line
Fixes #1104
Fixes # (issue)
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist:
Tagging @carlosalberto as requested 👍